-
Notifications
You must be signed in to change notification settings - Fork 712
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make unconteinerized build work on OSX #1028
Conversation
I don't understand how this even works... surely when entering the container it tries to build something that it doesn't know about? |
What don't you understand? It simply names the binary based on the host It fixes trying to use a binary from the wrong architecture when mixing From a conversation in Slack it seems @davkal may be having other problems On Wednesday, February 24, 2016, Tom Wilkie [email protected]
|
db62f8c
to
6b17a23
Compare
23b97ab
to
18964aa
Compare
Builds in container, and on Darwin. LGTM |
Pls hold off on this until I've had a chance to look at it, I have some concerns. |
I get this when trying to build using docker-machine on my mac:
|
@tomwilkie please take another look. I fixed it by moving all the codecgen dependencies to the non-containerized part (which is here they should be since codecgen depends on the host of whatever runs the non-containerized part) |
This now requires I have go installed, which I thought we'd decided against... |
No it doesn't. Have you actually tested it? As I already said, the makefile variables are used lazily unless assigned with
|
@2opremio how did you test the darwin build? Which command do you run? |
@davkal I have been relying on you to test the build in Darwin (I use a Linux VM). The purpose of this PR is to make you comfortable with the build, hence the PTAL :) |
@@ -1,5 +1,4 @@ | |||
FROM golang:1.5.3 | |||
ENV GO15VENDOREXPERIMENT 1 |
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
This command used to work Also, if I change the build container the .codecgen.go files are not rebuilt and I kinda think they should be. In general it makes me uncomfortable to have different dependancy trees inside the container to outside. |
Note both of these are minor issues. What precisely is the problem we're trying to solve here? |
I cant think of a nicer way of doing this, so assuming we still want to fix the build-in-container-then-build-on-a-mac-without-a-make-clean-inbetween problem, I'm LGTM. |
Yes please, easier it is to build in and out of container the better! |
Alright, then I will rebase the changes and ask you to take another look |
904d672
to
7d84993
Compare
Rebased. @foot Can you please test it so that we can merge it? (Ideally before it bit-rots again! :) ) |
7d84993
to
aead6d3
Compare
aead6d3
to
d7e9d13
Compare
|
But otherwise it works nicely! |
Rebased onto master. |
But circle is giving a funny permission error now so maybe i broke something.. |
That's because we now build |
* Get rid of GO15VENDOREXPERIMENT since it's enabled by default in Go >=1.6, just use go 1.6 if you want to build outside the container. * Stop using unset/env -u, just avoid adding env variables where needed. * Pass build flags consistently to codecgen. * Let the experimental/ directory be.
I think we were overcomplicating it. My last commit makes it much simpler (although it will only work when ugorji/go#148 is merged and we bump the dependency).
|
To be able to get rid of GO15VENDOREXPERIMENT ugorji/go#147
LGTM for me! |
Make unconteinerized build work on OSX
@davkal PTAL